It was definitely not my intention to introduce bugs, if that happened, I am really sorry.
The code was introduced for the following scenario:

• Tux is big
• Player presses and holds down key for the rest of the described sequence -> Tux is crawling
• Player crawls towards a slope -> Tux starts to slide on the slope
• Slope ends and Tux comes to a stop -> Tux remains in crawling animation

The original behavior - that your PR now restores - is that Tux sets the "duck" action. If you then press left or right, the action will switch from duck to crawling animation which looks a bit weird. In my opinion remaining in the crawl action looks much better than switching to duck action.
So m_was_crawling_before_slide should in my opinion not be set to false in case player stopped sliding due to friction.

At least that was my intention that Tux does not go to duck when it stops after sliding, but it seems that it is not working like that (I was pretty sure I tested this several times), so at this part your PR does not seem to change the behavior.
Anyway: The flag is used to skip the "duck" part of the sliding animation when Tux was crawling before (otherwise Tux would crawl, standup and then transit to slide again in the above described scenario [transition from crawl to slide]).

I remember now, why I was so sure that the described behavior is working: Please check out also my changes in #2810 . With these changes, the described behavior should work. Looks like you're in a flow right now, so maybe you could take all these information into account and do the ultimate fix. :-)

I remember now, why I was so sure that the described behavior is working: Please check out also my changes in #2810 . With these changes, the described behavior should work. Looks like you're in a flow right now, so maybe you could take all these information into account and do the ultimate fix. :-)

Can you be a little more verbose regarding this message, please? I'm afraid I don't understand what you mean. And also sorry for coming across as mean in the original PR message.

Sure, sorry for the confusion.

I thought that Tux would already remain in the crawl action when he was sliding before and comes to a stop while the down key is still pressed (but without left or right being pressed). I forgot that I added/fixed this in #2810 (among the other things that are mentionened in the PR description), so I thought your PR here would break this behavior. Maybe you want to have a look at #2810 and check if it either makes things better or maybe you have a better idea how to improve it otherwise.

Also I mixed this discussion here a bit up with the behaviour regrading m_was_crawling_before_slide, which is supposed to skip the first frames of the slide action when Tux is crawling and directly goes into the slide action. The first frames of the slide actions show Tux changing from standing to sliding, but this leads to animation glitches if Tux is already crawling.

I hope this makes it a bit clearer. Please let me know if it is still too confusing. :-)

I just tested both PRs together and they seem to work pretty independently of each other and both of them together seem to fix the bugs they set out to, so I think both are fine right now.

Perfect, thanks!